The file GPMVB1.ZIP contains files for a Visual Basic program that uses
DDE to create a form-based document in Microsoft Word for Windows (Winword).
I am posting it to illustrate some of what I have discovered about using DDE
to control Winword; if there are better ways to do these things, I'd love to
hear about it!
	The VB program is PROMNOTE.MAK, a VB project with six related files:

		DDEFORM.FRM
		DOCSELCT.FRM
		PROMNOTE.BAS
		PROMNOTE.FRM
		PROMNOTE.GBL
		WINWORD.BAS

The remaining file in the package is VBNOTE.DOT, a Winword 1.x template that
should be copied to your Winword template directory before running the VB
program.
	Running the VB program will call up a form that collects data for a
simple promissory note.  When data entry is complete, there is a button on the
form that can be used to call up Winword and create a promissory note using the
VBNOTE template.  VBNOTE.DOT has dde fields that read data out of the VB
program.  The dde fields are embedded in set fields that assign the result of
the dde field to a bookmark, which is then referenced and formatted where
applicable in the document; if you have a color monitor, the items in the
document that trace back to the VB form should show up in red.  A table at
the beginning of the Winword document summarizes the data from the VB program
used in the document.
	If Winword is not running, the program will attempt to start it up.
Because I don't include much in my path and have been too lazy to work on
configuration routines, the program looks for a winword.ini file in c:\winword
and d:\winword.  If it finds one, it assumes that directory is your winword
directory; otherwise, it asks for your winword directory.
	The "Get Data" button calls up another form that can be used to read
data back out of a promissory note created by the VB program (or any other
Winword file that uses the same bookmark names).  The data can then be edited
and used to create a new note based on the revised data.  You can also use the
revised data to update the existing note, but you have to do it manually, i.e.,
while the VB form is still onscreen, switch to the Winword document and
manually update all of its fields (press Control plus 5 on the numeric keypad
to select the entire document, then F9 to update the fields; you may have to
unlock the fields (Control + Shift + F11) first).  Ideally, the forms would be
better integrated, i.e., you would have a Winword macro that could call up the
VB program, etc., but I haven't gotten around to that aspect of the project.
	There are some undoubtedly cryptic comments sprinkled throughout the
code; the rest you'll have to figure out yourself.  Think of it as a DDE
adventure game!

			g.p.m.
		CIS No. 72040,110

1/5/92